Automatic or Automated Test Equipment (ATE) is any apparatus that performs tests on a device, known as the Device Under Test (DUT), using automation to quickly perform measurements and evaluate the test results. An ATE can be a simple computer controlled digital multimeter, or a complicated system containing dozens of complex test instruments (real or simulated electronic test equipment) capable of automatically testing and diagnosing faults in sophisticated electronic packaged parts or on Wafer testing, including System-On-Chips and Integrated circuits.
Contents |
ATE is widely used in the electronic manufacturing industry to test electronic components and systems after being fabricated. ATE is also used to test avionics and the electronic modules in automobiles. It is used in military applications like radar and wireless communication.
Semiconductor ATE, named for testing semiconductor devices, can test a wide range of electronic devices and systems, from simple components (resistors, capacitors, and inductors) to integrated circuits (ICs), printed circuit boards (PCBs), and complex, completely assembled electronic systems. ATE systems are designed to reduce the amount of test time needed to verify that a particular device works or to quickly find its faults before the part has a chance to be used in a final consumer product. To reduce manufacturing costs and improve yield, semiconductor devices should to be tested after being fabricated to prevent even a small number of defective devices ending up with consumer.
The Semiconductor ATE architecture consists of master controller (usually a computer) that synchronizes one or more source and capture instruments (listed below). Historically, custom-designed controllers or relays were used by ATE systems. The Device Under Test (DUT) is physically connected to the ATE by another robotic machine called a Handler or Prober and through a customized Interface Test Adapter (ITA) or "fixture" that adapts the ATE's resources to the DUT.
The Industrial PC is nothing but a normal desktop computer packaged in 19-inch rack standards with sufficient PCI / PCIe slots for accommodating the Signal simulator/sensing cards. This takes up the role of a controller in the ATE. Development of test applications and result storage is managed in this PC. Most modern semiconductor ATEs include multiple computer controlled instruments to source or measure a wide range of parameters. The instruments may include Digital Power Supplies (DPS), Parametric Measurement Units (PMU), Arbitrary Waveform Generators (AWG), Digitizers, Digital IOs, and utility supplies. The instruments perform different measurements on the DUT, and the instruments are synchronized so that they source and measure waveforms at the proper times. Based on the requirement of response-time, real-time systems are also considered for simulation and signal capturing.
The Mass interconnect is a connector interface between test instruments (PXI, VXI, LXI, GPIB, SCXI, & PCI) and devices/units under test (D/UUT). This section acts as a nodal point for signals going in/out between ATE and D/UUT.
For example, to measure a voltage of a particular semiconductor device, the Digital Signal Processing instruments in the ATE measure the voltage directly and send the results to a computer for signal processing, where the desired value is computed. This example shows that conventional instruments, like an Ammeter, may not be used in many ATEs due to the limited number of measurements the instrument could make, and the time it would take to use the instruments to make the measurement. One key advantage to using DSP to measure the parameters is time. If we have to calculate the peak voltage of an electrical signal and other parameters of the signal, then we have to employ a peak detector instrument as well as other instruments to test the other parameters. If DSP-based instruments are used, however, then a sample of the signal is made and the other parameters can be computed from the single measurement.
Not all devices are tested equally. Testing adds costs, so low cost components are rarely tested completely, whereas medical or high costs components (where reliability is important) are frequently tested.
But testing the device for all parameters may or may not be required depending on the device functionality and end user. For example if the device finds application in medical or life saving products then many of its parameters must be tested, and some of the parameters must be guaranteed. But deciding on the parameters to be tested is a complex decision based on cost vs yield. If the device is a complex digital device, with thousands of gates, then test fault coverage has to be calculated. Here again the decision is complex based on test economics, based on frequency, number and type of I/Os in the device and the end-use application.
ATE can be used on packaged parts (typical IC 'chip') or directly on the Silicon Wafer. Packaged parts use a handler to place the device on a customized interface board, whereas silicon wafers are tested directly with high precision probes. The ATE systems interact with the handler or prober to test the DUT.
ATE systems typically interface with an automated placement tool, called a "handler", that physically places the Device Under Test (DUT) on an Interface Test Adapter (ITA) so that it can be measured by the equipment. There may also be an Interface Test Adapter (ITA), a device just making electronic connections between the ATE and the Device Under Test (also called Unit Under Test or UUT), but also it might contain an additional circuitry to adapt signals between the ATE and the DUT and has physical facilities to mount the DUT. Finally, a socket is used to bridge the connection between the ITA and the DUT. A socket must survive the rigorous demands of a production floor, so they are usually replaced frequently.
Simple electrical interface diagram: ATE -> ITA -> DUT (package) <- Handler
Wafer based ATEs typically use a device called a Prober that moves across a silicon wafer to test the device.
Simple electrical interface diagram: ATE -> Prober -> Wafer (DUT)
One way to improve test time is to test multiple devices at once. ATE systems can now support having multiple "sites" where the ATE resources are shared by each site. Some resources can be used in parallel, others must be serialized to each DUT.
The ATE computer uses modern computer languages (like C, C++, Java, LabVIEW or Smalltalk) with additional statements to control the ATE equipment through standard and proprietary Application Programming Interfaces (API). Also some dedicated computer languages exists, like Abbreviated Test Language for All Systems (ATLAS). Automatic test equipment can also be automated using a Test execution engine such as National Instruments' TestStand, and Hiatronics' Hiatronic Development Suite.
Sometimes automatic test pattern generation is used to help design the series of tests.
Many ATE platforms used in the semiconductor industry output data using Standard Test Data Format (STDF)
Automatic test equipment diagnostics is the part of an ATE test that determines the faulty components. ATE tests perform two basic functions. The first is to test whether or not the Device Under Test is working correctly. The second is when the DUT is not working correctly, to diagnose the reason. The diagnostic portion can be the most difficult and costly portion of the test. It is typical for ATE to reduce a failure to a cluster or ambiguity group of components. One method to help reduce these ambiguity groups is the addition of analog signature analysis testing to the ATE system. Diagnostics are often aided by the use of flying probe testing.
The addition of a high-speed switching system to a test system’s configuration allows for faster, more cost-effective testing of multiple devices, and is designed to reduce both test errors and costs. Designing a test system’s switching configuration requires an understanding of the signals to be switched and the tests to be performed, as well as the switching hardware form factors available.
Several modular electronic instrumentation platforms are currently in common use for configuring automated electronic test and measurement systems. These systems are widely employed for incoming inspection, quality assurance, and production testing of electronic devices and subassemblies. Industry-standard communication interfaces link signal sources with measurement instruments in “rack-and-stack” or chassis-/mainframe-based systems, often under the control of a custom software application running on an external PC.
The General Purpose Interface Bus (GPIB) is an IEEE-488 (a standard created by the Institute of Electrical and Electronics Engineers) standard parallel interface used for attaching sensors and programmable instruments to a computer. GPIB is a digital 8-bit parallel communications interface capable of achieving data transfers of more than 8 Mbytes/s. It allows daisy-chaining up to 14 instruments to a system controller using a 24-pin connector. It is one of the most common I/O interfaces present in instruments and is designed specifically for instrument control applications. The IEEE-488 specifications standardized this bus and defined its electrical, mechanical, and functional specifications, while also defining its basic software communication rules. GPIB works best for applications in industrial settings that require a rugged connection for instrument control.
The original GPIB standard was developed in the late 1960s by Hewlett-Packard to connect and control the programmable instruments the company manufactured. The introduction of digital controllers and programmable test equipment created a need for a standard, high-speed interface for communication between instruments and controllers from various vendors. In 1975, the IEEE published ANSI/IEEE Standard 488-1975, IEEE Standard Digital Interface for Programmable Instrumentation, which contained the electrical, mechanical, and functional specifications of an interfacing system. This standard was subsequently revised in 1978 (IEEE-488.1) and 1990 (IEEE-488.2). The IEEE 488.2 specification includes the Standard Commands for Programmable Instrumentation (SCPI), which define specific commands that each instrument class must obey. SCPI ensures compatibility and configurability among these instruments.
The IEEE-488 bus has long been popular because it is simple to use and takes advantage of a large selection of programmable instruments and stimuli. Large systems, however, have the following limitations:
The LXI Standard defines the communication protocols for instrumentation and data acquisition systems using Ethernet. These systems are based on small, modular instruments, using low-cost, open-standard LAN (Ethernet). LXI-compliant instruments offer the size and integration advantages of modular instruments without the cost and form factor constraints of card-cage architectures. Through the use of Ethernet communications, the LXI Standard allows for flexible packaging, high-speed I/O, and standardized use of LAN connectivity in a broad range of commercial, industrial, aerospace, and military applications. Every LXI-compliant instrument includes an Interchangeable Virtual Instrument (IVI) driver to simplify communication with non-LXI instruments, so LXI-compliant devices can communicate with devices that are not themselves LXI compliant (i.e., instruments that employ GPIB, VXI, PXI, etc.). This simplifies building and operating hybrid configurations of instruments.
LXI instruments sometimes employ scripting using embedded test script processors for configuring test and measurement applications. Script-based instruments provide architectural flexibility, improved performance, and lower cost for many applications. Scripting enhances the benefits of LXI instruments, and LXI offers features that both enable and enhance scripting. Although the current LXI standards for instrumentation do not require that instruments be programmable or implement scripting, several features in the LXI specification anticipate programmable instruments and provide useful functionality that enhances scripting’s capabilities on LXI-compliant instruments.[2]
The VXI bus architecture is an open standard platform for automated test based on the VMEbus. Introduced in 1987, VXI uses all Eurocard form factors and adds trigger lines, a local bus, and other functions suited for measurement applications. VXI systems are based on a mainframe or chassis with up to 13 slots into which various VXI instrument modules can be installed.[3] The chassis also provides all the power supply and cooling requirements for the chassis and the instruments it contains. VXI bus modules are typically 6U in height.
PXI is a peripheral bus specialized for data acquisition and real-time control systems. Introduced in 1997, PXI uses the CompactPCI 3U and 6U form factors and adds trigger lines, a local bus, and other functions suited for measurement applications. PXI hardware and software specifications are developed and maintained by the PXI Systems Alliance.[4] More than 50 manufacturers around the world produce PXI hardware.[5]
The USB connects peripheral devices, such as keyboards and mice, to PCs. The USB is a Plug and Play bus that can handle up to 127 devices on one port, and has a theoretical maximum throughput of 480 Mbit/s (high-speed USB defined by the USB 2.0 specification). Because USB ports are standard features of PCs, they are a natural evolution of conventional serial port technology. However, it is not widely used in building industrial test and measurement systems for a number of reasons; for example, USB cables are not industrial grade, are noise sensitive, can accidentally become detached, and the maximum distance between the controller and the device is 30 m. Like RS-232, USB is useful for applications in a laboratory setting that do not require a rugged bus connection.
RS-232 is a specification for serial communication that is popular in analytical and scientific instruments, as well for controlling peripherals such as printers. Unlike GPIB, with the RS-232 interface, it is possible to connect and control only one device at a time. RS-232 is also a relatively slow interface with typical data rates of less than 20 kbytes/s. RS-232 is best suited for laboratory applications compatible with a slower, less rugged connection.
One of the most recently developed test system platforms employs instrumentation equipped with onboard test script processors combined with a high-speed bus. In this approach, one “master” instrument runs a test script (a small program) that controls the operation of the various “slave” instruments in the test system, to which it is linked via a high-speed LAN-based trigger synchronization and inter-unit communication bus. Scripting is writing programs in a scripting language to coordinate a sequence of actions.
This approach is optimized for small message transfers that are characteristic of test and measurement applications. With very little network overhead and a 100Mbit/sec data rate, it is significantly faster than GPIB and 100BaseT Ethernet in real applications.
The advantage of this platform is that all connected instruments behave as one tightly integrated multi-channel system, so users can scale their test system to fit their required channel counts cost-effectively. A system configured on this type of platform can stand alone as a complete measurement and automation solution, with the master unit controlling sourcing, measuring, pass/fail decisions, test sequence flow control, binning, and the component handler or prober. Support for dedicated trigger lines means that synchronous operations between multiple instruments equipped with onboard Test Script Processors that are linked by this high speed bus can be achieved without the need for additional trigger connections.[6]